summaryrefslogtreecommitdiff
path: root/old/oldmail/200106.txt
blob: 2273d18d7ed35c31272fed5173ec6d94be2409b7 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396
1397
1398
1399
1400
1401
1402
1403
1404
1405
1406
1407
1408
1409
1410
1411
1412
1413
1414
1415
1416
1417
1418
1419
1420
1421
1422
1423
1424
1425
1426
1427
1428
1429
1430
1431
1432
1433
[Dillo-dev]Dillo for the ipaq

From: Eduardo Marcel Macan <macan@co...> - 2001-06-29 17:48

Guys thank you for the *wonderful* work you are doing with dillo.
I am working with the guys of the familiar distribution 
(familiar.handhelds.org) and dillo is becoming the best choice for
use in a limited storage device like the ipaq.

I have just made a package for dillo out of today's snapshot,
and I must say It is just *GREAT* .

here is the .ipk package of dillo for the ipaq using 
the familiar GNU/Linux distribution.

http://www.metainfo.org/macan/ipaq/dillo_20010629-1_arm.ipk

And here is the screenshot of dillo on an iPAQ displaying slashdot:
http://www.metainfo.org/macan/ipaq/10-ipaq-dillo_slashdot.png

I am leaving for a 10 day break now, but when I am back I
hope to start contributing more to the dillo web browser! :)

Thank you all!
-- 
"If you have an apple and I have an apple and we exchange apples then you 
and I will still each have one apple. But if you have an idea and I have 
an idea and we exchange these ideas, then each of us will have two ideas."
George Bernard Shaw 



[Dillo-dev]Feature

From: Sebastian Geerken <S.Geerken@pi...> - 2001-06-27 13:45

Hi iPAQ users (and others).

Since tables may be used to set the width at which words are wrapped
(either explicitly by the "width" attribute, or implicitly by images
and long words), the text may become unreadable on small screens.

Dillo could change the rendering to prevent this, one simple
possibility is new option, "limit_text_width", which limits the word
wrap width (but not necessary the final page width) to the viewport
width. I've implemented this, it is available via CVS.

I've tested it a bit, browsing with a small window size. It is
probably a bit better than before, but don't expect too much, you
loose the overview over the page easily. There may be new options
(e.g. factors for size specification and images), but they will not be
part of the (soon released) version 0.6.0.

Please post your comments. Does this feature make sense? Any further
ideas? Should dillo try to render such pages at all in a "readable"
way? Etc.

Sebastian 



[Dillo-dev]Dillo-ssl (patch)

From: <torkel@ly...> - 2001-06-26 21:27

Attachments: dillo-ssl.patch.gz      https.c.gz      

Hi all.

Nice work with dillo! About the only browser that is lightweight enough
for my iPAQ. However... i kinda need cookies, https and auth for it to be
really useable. I hacked together some kind of SSL support for it, and
tested against apache/mod_ssl. Seems to be functional.

Included are two files, a cvs diff against yesterdays cvs, and a new file
"https.c" which goes in IO/. Add the -I's and -l's for openssl (in my case
0.9.5a, yeah, it's old, i know ;)

Since it's my first attempt at both dillo and ssl hacking, the approach
might be a bit off. Basically it's a combination of about: and http:
backends with some SSL inbetween.

Now all i gotta do is to find a place in the GUI for a padlock ;)

...and ofcourse implement cookies and auth.

Best regards,
T-Å 



Re: [Dillo-dev]locale

From: Martynas Jocius <atthis@de...> - 2001-06-23 16:50

Hi, Sebastian

On Sat, Jun 23, 2001 at 03:35:33PM +0200, Sebastian Geerken wrote:

> gtk_set_locale is intended for the user interface, but it probably
> works for this purpose, if your "system" language ($LANG and $LC_...)
> and the language of the documents you are viewing are the same.
>

I am not talking about the documents.
Bug 173 was inserted by me :). I am from Lithuania, small country in Europe
near the Baltic Sea. Native charset is iso-8859-13. I have no problems on
viewing any documents with lithuanian characters. But I was talking about
Dillo. For example, I bookmark a page and set a title with lithuanian
characters. I can't see them. 
Or I have to type some text with my native characters into the entry in 
the html page. I can't do that too...
Well, now it's ok, I fixed this :)

> BTW, there has been a discussion on the list, you can find it in the
> archive at:
[some addresses] 
Yes, discussian was about documents with Korean/Russian characters. As I
said, I have no problems at this point ;)

> Perhaps we can already implement a simple scheme dealing with 8-bit
> fonts, looking at what Gtk+ 1.2 already provides. Extending
> DwStyleFont by an encoding attribute might works. (Sorry, I'm no
> expert on this topic at all.)

So what about gtk_set_locale()? I think it's a good way. Maybe someday we
will make Dillo to understand i18n for the translations. 


--
Martynas 



Re: [Dillo-dev]locale

From: Sebastian Geerken <S.Geerken@pi...> - 2001-06-23 13:30

On Fri, Jun 22, Martynas Jocius wrote:
> Bug #173. Can't see/write native characters. Insert gtk_set_locale() into
> src/dillo.c line 80. :-)

gtk_set_locale is intended for the user interface, but it probably
works for this purpose, if your "system" language ($LANG and $LC_...)
and the language of the documents you are viewing are the same.

BTW, there has been a discussion on the list, you can find it in the
archive at:

http://www.geocrawler.com/archives/3/702/2001/5/0/5805536/
http://www.geocrawler.com/archives/3/702/2001/5/0/5806440/
http://www.geocrawler.com/archives/3/702/2001/5/0/5811325/
http://www.geocrawler.com/archives/3/702/2001/5/0/5812833/
http://www.geocrawler.com/archives/3/702/2001/5/0/5830229/
http://www.geocrawler.com/archives/3/702/2001/5/0/5833416/

Perhaps we can already implement a simple scheme dealing with 8-bit
fonts, looking at what Gtk+ 1.2 already provides. Extending
DwStyleFont by an encoding attribute might works. (Sorry, I'm no
expert on this topic at all.)

Sebastian 



[Dillo-dev]DwStyle memory leaks

From: Sebastian Geerken <S.Geerken@pi...> - 2001-06-22 16:13

Hi,

just a hint on warnings like "** WARNING **: 1 styles left": It seems
that the memory management works, except if the HTML parser is
interrupted. In this case, Html_close is not called, which will
normally unref all styles left in DilloHtml.

Sebastian 



Re: [Dillo-dev]HTML/CSS question

From: Sebastian Geerken <S.Geerken@pi...> - 2001-06-22 16:13

On Fri, Jun 22, Jörgen Viksell wrote:
> >does someone know how to replace the NOSHADE attribute of <hr> by CSS
> >attributes? In HTML4, it's deprecated, but there is no hint how to get
> >the same effect using CSS.
> 
> This would make it look similar:
> border: none; background-color: grey

I believe the ruler itself is the content, so it won't work.

Test the following in Amaya (I've installed 3.1):

<hr>
<hr style="border-style: none; background-color: #808080">
<hr style="border-style: none; background-color: #808080; padding: 5mm">

The first two look equally, the third has a gray rectangle *around*
the ruler.

Sebastian 



Re: [Dillo-dev]HTML/CSS question

From: Viksell <jorgen.viksell@te...> - 2001-06-22 12:23

>does someone know how to replace the NOSHADE attribute of <hr> by CSS
>attributes? In HTML4, it's deprecated, but there is no hint how to get
>the same effect using CSS.

This would make it look similar:
border: none; background-color: grey

// J=F6rgen 



[Dillo-dev]locale

From: Martynas Jocius <atthis@de...> - 2001-06-22 12:07

Hi,

Bug #173. Can't see/write native characters. Insert gtk_set_locale() into
src/dillo.c line 80. :-)

--
Martynas 



[Dillo-dev]HTML/CSS question

From: Sebastian Geerken <S.Geerken@pi...> - 2001-06-22 11:29

Hi,

does someone know how to replace the NOSHADE attribute of <hr> by CSS
attributes? In HTML4, it's deprecated, but there is no hint how to get
the same effect using CSS.

(I'm working on bug #168 (colors of <hr>'s), this could be solved
simple by DwStyle boxes, but I thought of making it already compliant
with a future CSS implementation, which will be based on DwStyle.)

Sebastian 



Re: [Dillo-dev][patch] File -> Close Window

From: Sam Dennis <sam@ma...> - 2001-06-21 16:12

On Thu, Jun 21, 2001 at 02:04:48PM +0300, Martynas Jocius wrote:
> I made another close window patch, maybe identical with last one. But I saw,
> that the memory is freed when destroying the window. Interface_quit()
> function is called when I do gtk_widget_destroy(). How does this work?

There's this little line in interface.c which reads:

gtk_signal_connect(GTK_OBJECT(bw->main_window), "destroy",
GTK_SIGNAL_FUNC(Interface_quit), bw);

So when the window is destroyed, gtk calls Interface_quit. 



Re: [Dillo-dev][patch] File -> Close Window

From: Martynas Jocius <atthis@de...> - 2001-06-21 12:00

Attachments: dillo-cvs-06-21-close_window.patch      

On Mon, Jun 18, 2001 at 09:22:38AM -0400, Jorge Arellano Cid wrote:
> Is very encouraging to see new people trying to get involved
> into dillo development, please don't get discouraged if you fail
> at your first attempts; it was the same for everyone of us ;-)

Thanks Jorge :)
I made another close window patch, maybe identical with last one. But I saw,
that the memory is freed when destroying the window. Interface_quit()
function is called when I do gtk_widget_destroy(). How does this work?

--
Martynas 



[Dillo-dev]RGBA data (was: Misc)

From: Sebastian Geerken <S.Geerken@pi...> - 2001-06-20 15:48

On Tue, Jun 19, I wrote:
> - Image transparency 2: If you have something like
> 
> <table>
> <tr>
> <td bgcolor=red><img src="foo.png">
> <td bgcolor=green><img src="foo.png">
> </table>
> 
> the first image will, correctly, have have a red background, but
> the second, incorrectly, too, since they share the same dicache
> buffer. So the transparency should somehow stored in the dicache
> buffer, instead of replaced by a background color.

If there are no objections, I'll start to modify the image code to use
RGBA data instead of RGB.

Sebastian 



[Dillo-dev]Misc

From: Sebastian Geerken <S.Geerken@pi...> - 2001-06-19 16:45

Hi all,

I have been working on borders and colors, now they work for table
(just uploaded), although a bit polishing is needed. However, some
notes:

- What happened to the <font> implementation? I've now activated
<font color> (but not face), of course inside an "if
(!prefs.force_my_colors)", since this makes some colored tables
more readable.

- Image transparency 1: I've modified Png_datarow_callback to use
the background color passed to a_Image_new, by replacing
prefs.bg_color by png->Image->bg_color. I don't know very much
about image processing, but this seems the way this should be
handled (?).

- Image transparency 2: If you have something like

<table>
<tr>
<td bgcolor=red><img src="foo.png">
<td bgcolor=green><img src="foo.png">
</table>

the first image will, correctly, have have a red background, but
the second, incorrectly, too, since they share the same dicache
buffer. So the transparency should somehow stored in the dicache
buffer, instead of replaced by a background color.

Sebastian 



Re: [Dillo-dev][patch] File -> Close Window

From: Jorge Arellano Cid <jcid@ne...> - 2001-06-18 13:52

Martynas,


> There was a bug #87 about closing window. There's a small patch which fixes
> this.

Is very encouraging to see new people trying to get involved
into dillo development, please don't get discouraged if you fail
at your first attempts; it was the same for everyone of us ;-)

I ask, at the web page, to be sent information about personal
skills, but I understand if they don't send any. That's just to
know in which part of dillo their knowledge would fit better, and
also to guide or hint their progress.

Jorge.- 



Re: [Dillo-dev]tables: COLSPAN

From: Sebastian Geerken <S.Geerken@pi...> - 2001-06-14 22:58

On Thu, Jun 14, Sam Dennis wrote:
> On Thu, Jun 14, 2001 at 06:59:05PM +0200, Sebastian Geerken wrote:
> [...]
> > Fixed and committed.
> >
> > Sebastian
>
> I'm sorry but it doesn't look very fixed to me, I'm getting almost exactly the
> same results here.

What images do you use? I tested it with

<table>
<tr>
<td colspan=2><img src="maj00s.gif" width=200 height=100>
<td rowspan=2><img src="maj00s.gif" width=100 height=200>
<tr>
<td rowspan=2><img src="maj00s.gif" width=100 height=200>
<td><img src="maj00s.gif" width=100 height=100>
<tr>
<td colspan=2><img src="maj00s.gif" width=200 height=100>
</table>

and got

+---------+ +---+
| | | |
+---------+ | |
+---+ +---+ | |
| | | | | |
| | +---+ +---+
| | +---------+
| | | |
+---+ +---------+

With some certain image sizes, the result is indeed not perfect, see
example in doc/DwTable.txt.


Sebastian 



Re: [Dillo-dev]tables: COLSPAN

From: Sam Dennis <sam@ma...> - 2001-06-14 21:35

On Thu, Jun 14, 2001 at 06:59:05PM +0200, Sebastian Geerken wrote:
> On Wed, Jun 13, Sam Dennis wrote:
> > It may have been a while since I wrote any real HTML, but I think I'd be
> > correct in thinking that the following table shouldn't be rendered as
> > illustrated:
> > [...]
> 
> Fixed and committed.
> 
> Sebastian

I'm sorry but it doesn't look very fixed to me, I'm getting almost exactly the
same results here. 



Re: [Dillo-dev]tables: COLSPAN

From: Sebastian Geerken <S.Geerken@pi...> - 2001-06-14 16:54

On Wed, Jun 13, Sam Dennis wrote:
> It may have been a while since I wrote any real HTML, but I think I'd be
> correct in thinking that the following table shouldn't be rendered as
> illustrated:
> [...]

Fixed and committed.

Sebastian 



Re: [Dillo-dev][patch] File -> Close Window

From: Sam Dennis <sam@ma...> - 2001-06-14 11:59

On Thu, Jun 14, 2001 at 01:39:05PM +0300, Martynas Jocius wrote:
> On Thu, Jun 14, 2001 at 11:56:38AM +0100, Sam Dennis wrote:
> 
> > When a window is closed, significantly more needs to be done than simply
> > destroying the window. Interface_quit performs all the necessary actions and
> > should almost certainly be called when the close window function is used.
> 
> Ok, sorry. I'll try to fix it. Just I'm very new in Dillo sources.
> What about adding:
> if (bw->main_window != NULL)
> gtk_widget_destroy(bw->main_window);
> 
> into Interface_quit? And then call Interface_quit when the menu item is
> clicked? This will require a lot more changes in sources. 

Sorry about this, but ignore everything I said, I'm not at my sharpest today :)

Interface_quit is the handler for destroying the main window, so you don't
have to worry about calling it. 



Re: [Dillo-dev][patch] File -> Close Window

From: Martynas Jocius <atthis@de...> - 2001-06-14 11:35

On Thu, Jun 14, 2001 at 11:56:38AM +0100, Sam Dennis wrote:

> When a window is closed, significantly more needs to be done than simply
> destroying the window. Interface_quit performs all the necessary actions and
> should almost certainly be called when the close window function is used.

Ok, sorry. I'll try to fix it. Just I'm very new in Dillo sources.
What about adding:
if (bw->main_window != NULL)
gtk_widget_destroy(bw->main_window);

into Interface_quit? And then call Interface_quit when the menu item is
clicked? This will require a lot more changes in sources. 

--
Martynas 



Re: [Dillo-dev][patch] File -> Close Window

From: Sam Dennis <sam@ma...> - 2001-06-14 10:47

On Thu, Jun 14, 2001 at 12:28:57PM +0300, Martynas Jocius wrote:
> Hi,
> 
> There was a bug #87 about closing window. There's a small patch which fixes
> this. 
> 
> --
> Martynas

> /*
> - * ?
> + * Close single window. Exit Dillo if only one window is. 
> */
> void a_Commands_close_callback(GtkWidget *widget, gpointer client_data)
> {
> + BrowserWindow *bw = (BrowserWindow *)client_data;
> + Interface_destroy_window(bw->main_window);
> }

When a window is closed, significantly more needs to be done than simply
destroying the window. Interface_quit performs all the necessary actions and
should almost certainly be called when the close window function is used. 



[Dillo-dev][patch] File -> Close Window

From: Martynas Jocius <atthis@de...> - 2001-06-14 10:25

Attachments: dillo-cvs-close_window.atthis.patch      

Hi,

There was a bug #87 about closing window. There's a small patch which fixes
this. 

--
Martynas 



Re: [Dillo-dev]table algorithm (was: tables: COLSPAN)

From: Sam Dennis <sam@ma...> - 2001-06-14 10:10

On Fri, Jan 05, 1990 at 01:34:08AM -0900, Jon Bradley wrote:
> 
> It is impossible to access the CVS. I have done it before, back when
> 0.3.0 was release. But it appears all information about the CVS is gone
> from the website AND the knownledge base.
> 
> Have you closed down the CVS to the public? I would like to see how
> dillo is looking with frames.

AFAIK, anonymous CVS is working perfectly, and I'm afraid that you won't be
seeing frames yet, only tables. Although my frames code should be ready in the
not-so-distant future... 



Re: [Dillo-dev]tables: COLSPAN

From: Sebastian Geerken <S.Geerken@pi...> - 2001-06-14 09:15

On Wed, Jun 13, Sam Dennis wrote:
> I was going to congratulate you on actually making that system work, but now,
> having actually seen its output, I've decided that it needs a bit more work.

This is what bug reports are for. :-)

> It may have been a while since I wrote any real HTML, but I think I'd be
> correct in thinking that the following table shouldn't be rendered as
> illustrated:
> [...]

This one is fixed, but I've not yet uploaded the change, there are
still a few more bugs.

Sebastian 



Re: [Dillo-dev]dillo CVS

From: Jon Bradley <kreator@mo...> - 2001-06-13 21:58

Please disgrad the last message I just sent about an impossible CVS.

=-=-=-=-=-=-=-=-=-=-=-=
Email: kreator@gc...
bbs: telnet://toga.cx
=-=-=-=-=-=-=-=-=-=-=-=


On 13 Jun 2001, Sebastian Geerken wrote:

> On Thu, Jan 04, Jon Bradley wrote:
> >
> > Hi,
> >
> > I am trying to login to the dillo CVS, so I searched the dillo website,
> > where I found no info on the CVS. I then got to the knowledge base of
> > Mail Archives, where I found a message showing how to login to the CVS,
> > although, the knowledge base has some type of filter for email addresses?
> > So again, I was not able to login.
> >
> > I am a novice at CVS, can someone please describe what I am suppose to do,
> > or atleast what my CVSROOT var is suppose to be? Thanks.
>
> The commands are:
>
> cvs -d:pserver:anonymous@cv...:/cvsroot/dillo login
> cvs -z8 -d:pserver:anonymous@cv...:/cvsroot/dillo co dillo
>
> There is also information at the SourceForge side, at
> http://so....net/cvs/?group_id=603. Perhaps this should added to
> home page, Jorge?
>
> Sebastian
>
> _______________________________________________
> Dillo-dev mailing list
> Dillo-dev@li...
> http://lists.so....net/lists/listinfo/dillo-dev
> 



Re: [Dillo-dev]table algorithm (was: tables: COLSPAN)

From: Jon Bradley <kreator@mo...> - 2001-06-13 21:56

It is impossible to access the CVS. I have done it before, back when
0.3.0 was release. But it appears all information about the CVS is gone
from the website AND the knownledge base.

Have you closed down the CVS to the public? I would like to see how
dillo is looking with frames.

=-=-=-=-=-=-=-=-=-=-=-=
Email: kreator@gc...
bbs: telnet://toga.cx
=-=-=-=-=-=-=-=-=-=-=-=


On 13 Jun 2001, Sebastian Geerken wrote:

> On Tue, Jun 12, I wrote:
> > Optimal := what you would have as a result, according to the
> > autolayout algorithm suggested in Appendix B of the HTML
> > spec, for tables *without* COLSPAN.
>
> Well, sorry, I was a bit sloppy in reading the text. My code is (as
> most other web browsers) based on an other definition:
>
> 1. All columns have have the same width W, except:
>
> - W is less than the minimal column width, or
> - W is greater than the maximal column width.
>
> Furthermore, W is
>
> - less than all minimal widths of columns not having W as
> width, and
> - greater than all maximal widths of columns not having W as
> width.
>
> 2. The table tries to use exactly the whole available width, except
> if it is not possible, because the available width is
> less/greater than the minimal/maximal table width.
>
> (BTW, there is a bug in the CVS, but I've fixed this, and will upload
> it soon.)
>
> A simple example: The table
>
> <table>
> <tr>
> <td>
> Blah Blah Blah Blah Blah Blah Blah Blah Blah Blah
> <td>
> Blah Blah Blah Blah Blah Blah Blah Blah Blah Blah
> Blah Blah Blah Blah Blah Blah Blah Blah Blah Blah
> </table>
>
> would, by the W3C algorithm, rendered as:
>
> +------------+----------------------+
> | Blah Blah | Blah Blah Blah Blah |
> | Blah Blah | Blah Blah Blah Blah |
> | Blah Blah | Blah Blah Blah Blah |
> | Blah Blah | Blah Blah Blah Blah |
> | Blah Blah | Blah Blah Blah Blah |
> +------------+----------------------+
>
> while most browsers render this:
>
> +-----------------+-----------------+
> | Blah Blah Blah | Blah Blah Blah |
> | Blah Blah Blah | Blah Blah Blah |
> | Blah Blah Blah | Blah Blah Blah |
> | Blah | Blah Blah Blah |
> | | Blah Blah Blah |
> | | Blah Blah Blah |
> | | Blah Blah |
> +-----------------+-----------------+
>
> Note that the W3C algorithm may have very "unaesthetical" results when
> the columns differ quite much in there maximal length, while having
> comparable content length (number of characters), e.g. if one column
> consists of many small paragraphs, whereas another consists of few
> long paragraphs.
>
> I think we should follow the common implementations, which authors may
> have in mind, instead of the W3C recommendation. Different opinions?
>
>
> Sebastian
>
> _______________________________________________
> Dillo-dev mailing list
> Dillo-dev@li...
> http://lists.so....net/lists/listinfo/dillo-dev
> 



Re: [Dillo-dev]tables: COLSPAN

From: Sam Dennis <sam@ma...> - 2001-06-13 19:33

On Wed, Jun 13, 2001 at 08:29:08PM +0200, Sebastian Geerken wrote:
> > Currently, I'm working on COLSPAN. [...]
> 
> Just uploaded, together with some bugfixes.
> 
> Sebastian

I was going to congratulate you on actually making that system work, but now,
having actually seen its output, I've decided that it needs a bit more work.

It may have been a while since I wrote any real HTML, but I think I'd be
correct in thinking that the following table shouldn't be rendered as
illustrated:

<table>
<tr>
<td colspan=2><img src=1.png></td>
<td rowspan=2><img src=2.png></td>
</tr>
<tr>
<td rowspan=2><img src=3.png></td>
<td><img src=4.png></td>
</tr>
<tr>
<td colspan=2><img src=5.png></td>
</tr>
</table>

+-------+ +---+
| | | |
+-------+ | |
+---++---+ | |
| || | +---+
| |+---+
| |+-------+
+---+| |
+-------+

But don't take this the wrong way, I'm impressed that you managed to get that
approach working at all! 



Re: [Dillo-dev]tables: COLSPAN

From: Sebastian Geerken <S.Geerken@pi...> - 2001-06-13 18:22

> Currently, I'm working on COLSPAN. [...]

Just uploaded, together with some bugfixes.

Sebastian 



Re: [Dillo-dev]dillo CVS

From: Jorge Arellano Cid <jcid@ne...> - 2001-06-13 14:27

Hi!

> [CVS]
> The commands are:
>
> cvs -d:pserver:anonymous@cv...:/cvsroot/dillo login
> cvs -z8 -d:pserver:anonymous@cv...:/cvsroot/dillo co dillo
>
> There is also information at the SourceForge side, at
> http://so....net/cvs/?group_id=603. Perhaps this should added to
> home page, Jorge?

Done, in [Links] section.


Jorge. 



[Dillo-dev]table algorithm (was: tables: COLSPAN)

From: Sebastian Geerken <S.Geerken@pi...> - 2001-06-13 13:34

On Tue, Jun 12, I wrote:
> Optimal := what you would have as a result, according to the
> autolayout algorithm suggested in Appendix B of the HTML
> spec, for tables *without* COLSPAN.

Well, sorry, I was a bit sloppy in reading the text. My code is (as
most other web browsers) based on an other definition:

1. All columns have have the same width W, except:

- W is less than the minimal column width, or
- W is greater than the maximal column width.

Furthermore, W is

- less than all minimal widths of columns not having W as
width, and
- greater than all maximal widths of columns not having W as
width.

2. The table tries to use exactly the whole available width, except
if it is not possible, because the available width is
less/greater than the minimal/maximal table width.

(BTW, there is a bug in the CVS, but I've fixed this, and will upload
it soon.)

A simple example: The table

<table>
<tr>
<td>
Blah Blah Blah Blah Blah Blah Blah Blah Blah Blah
<td>
Blah Blah Blah Blah Blah Blah Blah Blah Blah Blah
Blah Blah Blah Blah Blah Blah Blah Blah Blah Blah
</table>

would, by the W3C algorithm, rendered as:

+------------+----------------------+
| Blah Blah | Blah Blah Blah Blah |
| Blah Blah | Blah Blah Blah Blah |
| Blah Blah | Blah Blah Blah Blah |
| Blah Blah | Blah Blah Blah Blah |
| Blah Blah | Blah Blah Blah Blah |
+------------+----------------------+

while most browsers render this:

+-----------------+-----------------+
| Blah Blah Blah | Blah Blah Blah |
| Blah Blah Blah | Blah Blah Blah |
| Blah Blah Blah | Blah Blah Blah |
| Blah | Blah Blah Blah |
| | Blah Blah Blah |
| | Blah Blah Blah |
| | Blah Blah |
+-----------------+-----------------+

Note that the W3C algorithm may have very "unaesthetical" results when
the columns differ quite much in there maximal length, while having
comparable content length (number of characters), e.g. if one column
consists of many small paragraphs, whereas another consists of few
long paragraphs.

I think we should follow the common implementations, which authors may
have in mind, instead of the W3C recommendation. Different opinions?


Sebastian 



Re: [Dillo-dev]dillo CVS

From: Sebastian Geerken <S.Geerken@pi...> - 2001-06-13 13:34

On Thu, Jan 04, Jon Bradley wrote:
> 
> Hi,
> 
> I am trying to login to the dillo CVS, so I searched the dillo website,
> where I found no info on the CVS. I then got to the knowledge base of
> Mail Archives, where I found a message showing how to login to the CVS,
> although, the knowledge base has some type of filter for email addresses?
> So again, I was not able to login.
> 
> I am a novice at CVS, can someone please describe what I am suppose to do,
> or atleast what my CVSROOT var is suppose to be? Thanks.

The commands are:

cvs -d:pserver:anonymous@cv...:/cvsroot/dillo login
cvs -z8 -d:pserver:anonymous@cv...:/cvsroot/dillo co dillo

There is also information at the SourceForge side, at
http://so....net/cvs/?group_id=603. Perhaps this should added to
home page, Jorge?

Sebastian 



[Dillo-dev]dillo CVS

From: Jon Bradley <kreator@mo...> - 2001-06-13 01:38

Hi,

I am trying to login to the dillo CVS, so I searched the dillo website,
where I found no info on the CVS. I then got to the knowledge base of
Mail Archives, where I found a message showing how to login to the CVS,
although, the knowledge base has some type of filter for email addresses?
So again, I was not able to login.

I am a novice at CVS, can someone please describe what I am suppose to do,
or atleast what my CVSROOT var is suppose to be? Thanks.

=-=-=-=-=-=-=-=-=-=-=-=
Email: kreator@gc...
bbs: telnet://toga.cx
=-=-=-=-=-=-=-=-=-=-=-= 



Re: [Dillo-dev]tables: COLSPAN

From: Sebastian Geerken <S.Geerken@pi...> - 2001-06-12 18:49

On Tue, Jun 12, Sam Dennis wrote:
> It seems to me that your algorithm may have some problems with tables using
> combinations of ROWSPAN and COLSPAN, to take an extreme example:
> 
> +-------+---+
> | A | |
> +---+---+ B +
> | | D | |
> | C +---+---+
> | | E |
> +---+-------+
> 
> Would your algorithm handle this well? The description you've given doesn't
> suggest so.

Tested ... works. :-)

Table rendering is (in both implementations) done in three steps:

1. Calculating minimal and maximal column widths,
2. calculating the column widths, and
3. calculating the column heights.

Only step 1 and 2 (which are changed) deal with COLSPAN, and only step
3 deals with ROWSPAN, so there is no problem. Note that when rendering
documents (as opposed to GUIs), both dimensions are not symmetric,
most is determined by the viewport width, the height plays a much less
important role.

> Also, there is perhaps the issue of what `optimal' means in table layout
> anyhow.

Optimal := what you would have as a result, according to the
autolayout algorithm suggested in Appendix B of the HTML
spec, for tables *without* COLSPAN.

(BTW, this is what led me to the idea of recursive tables: if COLSPAN
is a problem, try to find subtables and so eliminate COLSPAN.)

E.g., the following layout is optimal:

+------+-------------------------------+
| Blah | Blah Blah Blah Blah Blah Blah |
| | Blah Blah Blah Blah |
+------+-------------------------------+

|------------ viewport width ------------|

while the following, trivial, is not:

+------------------+-------------------+
| Blah | Blah Blah Blah |
| | Blah Blah Blah |
| | Blah Blah Blah |
| | Blah |
+------------------+-------------------+

This should also work for COLSPAN:

+--------------------------------------+
|BlahBlahBlahBlahBlahBlahBlahBlahBlah |
+------+-------------------------------+
| Blah | Blah Blah Blah Blah Blah Blah |
| | Blah Blah Blah Blah |
+------+-------------------------------+

instead of:

+--------------------------------------+
|BlahBlahBlahBlahBlahBlahBlahBlahBlah |
+------------------+-------------------+
| Blah | Blah Blah Blah |
| | Blah Blah Blah |
| | Blah Blah Blah |
| | Blah |
+------------------+-------------------+

Note that my algorithm isn't optimal in some cases, an alternative
would be "real" optimization, but this will be even more complicated
and slow.

> Finally, your solution looks _very_ awkward to code. I don't like the idea of
> a recursive algorithm for table layout in the first place and it might present
> more problems than it solves, mightn't a little thought go towards a simpler
> algorithm? (Not that I've got one...)

I don't think that recursion is complex per se, often problems can
solved much simpler that way. In this case, the code (it is nearly
complete) isn't much more complex than before (and not slower),
although I must admit that the idea might be a bit strange.

Maybe a look at other browsers might be useful, but I'll complete it
now, it can anyway changed in the future.


Sebastian 



Re: [Dillo-dev]tables: COLSPAN

From: Sam Dennis <sam@ma...> - 2001-06-12 15:03

It seems to me that your algorithm may have some problems with tables using
combinations of ROWSPAN and COLSPAN, to take an extreme example:

+-------+---+
| A | |
+---+---+ B +
| | D | |
| C +---+---+
| | E |
+---+-------+

Would your algorithm handle this well? The description you've given doesn't
suggest so.

Also, there is perhaps the issue of what `optimal' means in table layout
anyhow.

Finally, your solution looks _very_ awkward to code. I don't like the idea of
a recursive algorithm for table layout in the first place and it might present
more problems than it solves, mightn't a little thought go towards a simpler
algorithm? (Not that I've got one...) 



Re: [Dillo-dev]tables: COLSPAN

From: Sebastian Geerken <S.Geerken@pi...> - 2001-06-11 18:02

On Mon, Jun 11, Sam Dennis wrote:
> Sorry if this may mean that a lot of time has been wasted in reinventing the
> wheel, but there are quite extensive notes on tables in general and layout algorithms in
> particular in the HTML specs.

I use, more or less, the algorithm described in the spec, but I handle
cells spanning several columns in a different way, since the described
algorithm is sufficient for tabled data, but not for "layout tables".
Not that that tables are the best way for page layout, but some pages
would be unreadable otherwise.

This is the part in the spec about the problem:

For cells that span multiple columns, a simple approach consists of
apportioning the min/max widths evenly to each of the constituent
columns. A slightly more complex approach is to use the min/max
widths of unspanned cells to weight how spanned widths are
apportioned. Experiments suggest that a blend of the two approaches
gives good results for a wide range of tables.

But I'm aiming towards perfect, not just good, results. ;-)

Suppose the following table:

<table>
<tr>
<td colspan="2"><img src="banner.gif" width="500" height="50">
<tr>
<td>
Links:<br>
...
<td>
A long text over several lines blah blah blah ...
</table>

An optimal layout (what my algorithm does indeed :-) would result in:

,----------------------------------------.
| Banner |
`----------------------------------------'

Links: A long text over several lines blah blah blah
... blah blah ...
|--------------------- viewport width ---------------------|


The result of the simple algorithm in the spec:

,--------------------------------------------------.
| Banner |
`--------------------------------------------------'

Links: A long text over several lines blah
... blah blah ...
|--------------------- viewport width ---------------------|


The complex approach would have a similar effect, since the minimal
widths of both text cells are quite similar, this would make both
weights for the minimum nearly equal, and so (in this case) determine
the same column widths.


Sebastian 



Re: [Dillo-dev]tables: COLSPAN

From: Sam Dennis <sam@ma...> - 2001-06-11 14:41

On Fri, Jun 08, 2001 at 02:14:47PM +0200, Sebastian Geerken wrote:
> Hi,
> 
> first, FYI: there have been some updates of the table implementation,
> image maps and COLSPAN now work. For finding text, the best solution
> is probably to add a new method DwWidget::find_text, which searches
> recursively in DwContainer's.
> 
> Currently, I'm working on COLSPAN. As you may have noticed, the
> current implementation does not work well for large spanning
> columns. The approach I'm using is to divide the table recursively
> into subtables. This is not always possible, so sometimes the cells
> have to be "divided", which makes the rendering not optimal, but
> reasonable, the effect should be small in most cases. An optimal
> solution would otherwise be complicated and slow.

Sorry if this may mean that a lot of time has been wasted in reinventing the
wheel, but there are quite extensive notes on tables in general and layout algorithms in
particular in the HTML specs.

http://www.w3.org/TR/html4/appendix/notes.html#notes-table might be worth a
look. 



Re: [Dillo-dev]tables: COLSPAN

From: Sebastian Geerken <S.Geerken@pi...> - 2001-06-08 12:43

On Fri, Jun 08, I wrote:
> first, FYI: there have been some updates of the table implementation,
> image maps and COLSPAN now work.
^^^^^^^
Of course, I meant ROWSPAN.

Sebastian 



[Dillo-dev]tables: COLSPAN

From: Sebastian Geerken <S.Geerken@pi...> - 2001-06-08 12:13

Hi,

first, FYI: there have been some updates of the table implementation,
image maps and COLSPAN now work. For finding text, the best solution
is probably to add a new method DwWidget::find_text, which searches
recursively in DwContainer's.

Currently, I'm working on COLSPAN. As you may have noticed, the
current implementation does not work well for large spanning
columns. The approach I'm using is to divide the table recursively
into subtables. This is not always possible, so sometimes the cells
have to be "divided", which makes the rendering not optimal, but
reasonable, the effect should be small in most cases. An optimal
solution would otherwise be complicated and slow.

I'm not sure if this is the simplest approach, I've also had other
ideas, but did not succeed in developing them further to an algorithm.
I've appended an extract of the new documentation, I'm now working on
the implementation. If someone knows a better approach, let me know
it!

Sebastian

----------------------------------------------------------------------

A table is divided into subtables, until single columns are
left. Cells spanning the whole width are removed before dividing
further. Example:

+---+-------+---+
| A | B | C |
+---+-------+---+
| D | E |
+---+-------+---+
| F | G | H |
+---+-------+---+
' ' ` `
' ' ` `
+---+-------+ +---+
| A | B | | C |
+---+-------+ +---+
removed --> | D | | E |
+---+-------+ +---+
| F | G | | H |
+---+-------+ +---+
' ' ` ` final
' ' ` `
+---+ +-------+
| A | | B | <-.
+---+ +-------+ >- removed
| F | | G | <-' 
+---+ +-------+
final ' ' ` `
' ' ` `
[empty] [empty]
final final

If table cells overlap horizontally, they are (virtually) divided
(resulting in a non optimal layout):

+-------+---+---+
| A | B | C |
+---+---+---+---+
| D | E |
+---+-----------+
' ' ` `
' ' ` `
+-------+ +---+---+
| A | | B | C |
+---+---+ +---+---+
| D |1/3| | 2/3 E |
| | E | | |
+---+---+ +-------+

Calculating extremes
--------------------
minimal/maximal width (sub table) =
- for single column: maximum of all minimal/maximal widths
- otherwise: maximum of
- all minimal/maximal widths of cells spanning
the whole width, and
- the sum of the minimal/maximal widths of the sub
tables

Calculating column widths
-------------------------
The calculation is based on an available width, which is, at the top,
the width set by a_Dw_widget_set_width, corrected by the minimal and
maximal width of the whole table. At each level, the available width
is always between the minimal and the maximal width of the subtable.

For single columns, the width is the available width. Otherwise, use
the simple iteration [described in the old DwTable.txt] on the
subtables, excluding the columns spanning the whole subtable width, to
get the width of the subtables. After this, apply this recursively on
all subtables, with the subtable width as available width. 



Re: [Dillo-dev]can not visit dillo.so....net

From: Jorge Arellano Cid <jcid@ne...> - 2001-06-04 19:05

Li,

> [...]
> Why can I not visit http://dillo.so....net now?

You SHOULD be able to see it!!! (I can)

If you can't visit it for an extended period, you can blame
your Internet Service Provider (ISP). Just as Livio said, source
forge has been under some troubles lately, but AFAIK that's over.

Jorge.- 



Re: [Dillo-dev]can not visit dillo.so....net

From: Livio Baldini Soares <livio@li...> - 2001-06-04 14:31

Hi liqx!

Qiaoxia,Li writes:
> Hi,
> Where can I download dillo-0.5.1,Why can I not visit http://
> dillo.so....net now?

Sourceforge is sometimes down... specially nowadays... But when
it's not you can get dillo-0.5.1 at:

http://download.so....net/dillo/dillo-0.5.1.tar.gz

best regards,

-- 
Livio <livio@li...> 



[Dillo-dev]can not visit dillo.so....net

From: Qiaoxia,Li <liqx@st...> - 2001-06-04 00:46

Attachments: Message as HTML      

SGksDQpXaGVyZSBjYW4gSSBkb3dubG9hZCBkaWxsby0wLjUuMSxXaHkgY2FuIEkgbm90IHZpc2l0
IGh0dHA6Ly9kaWxsby5zb3VyY2Vmb3JnZS5uZXQgbm93Pw0KcmVnYXJkcywNCmxpcXgNCg0K 



[Dillo-dev]File selection patch (again :)

From: Livio Baldini Soares <livio@li...> - 2001-06-03 04:54

Hello!

I'm sending (again) my updated patch for file selection while saving
pages or links. As Holger Rapp suggested, I have removed the modal
type windows, now they're like any dialog window.

The patch is simple (against 02-Jun CVS), and it's at:
http://www.linux.ime.usp.br/~livio/dillo/file_select_new.diff

Also, I think I'm willing to implement the Downloads scheme
described in [Project Notes], becasue in my opinion it's another great
TODO... Has anybody started anything on this?

PS: Sebastian, nice work on the tables! I was really happy when I saw
sourforge.net being rendered in a "readable way! I know it's still a
it buggy, but we'll work it out with time... Thanks!

best regards to all,

-- 
Livio <livio@li...> 



Re: [Dillo-dev]authentification

From: Jorge Arellano Cid <jcid@ne...> - 2001-06-01 09:44

Hi!


On Thu, 31 May 2001, Didier Bretin wrote:

> Hello,
>
> Dillo looks good :o). Go on !!!!

Thanks!

> Have you planned to deal with authentification ?

Sure, I have an ancient patch from Marcos Ram=EDrez that was
waiting for DilloUrl... If you're willing to work on it, I can
send you the patch so you can start from there.


Jorge.- 



Re: [Dillo-dev]authentification

From: Jorge Arellano Cid <jcid@ne...> - 2001-06-01 04:22

Hi!

On Thu, 31 May 2001, Alexey F. Bekish wrote:

> How from all it nsubscribe????

???

How to unsubscribe?

Go to dillo's home page, follow the [Mailing List] link, click
on the "Visit subscribers list" button, click your entry, enter
your password and click "unsubscribe" button!

Maybe sending an email with "unsubscribe" as subject could also
do the trick.


Jorge.-