[isf-wifidog] Request for comments, portal customization mechanisms

[Max Horváth]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Well, I'm not talking about the new design that much ...

On the current design I had to add Ids to the content elements of the  
administration interface for example, as I had absolutely no chance  
to explicitly apply css properties to some elements ... but it's just  
been the administration interface ... the rest is great now ...

Cheers, Max!

Am 27.03.2006 um 05:43 schrieb Benjamin Crulli:

> I told to benoit on irc that it looked fine to me.
> I don't see why we would need ids on elements that are in multiple
> instances on the page.
>
> On 3/26/06, Max Horváth <max.horvath at maxspot.de> wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Well, I really like the idea ... it's a great to remove SMARTY
>> templating and makes the system much more flexible. Really nice!
>>
>> The only suggestion I'd like to make is to add CSS Ids to every
>> element ... that's what I learned by customizing the layout of
>> maxspot ... some thing couldn't be catched by CSS without adding
>> specific Ids ...
>>
>> Besides that I'd like to add one suggestion ... it hasn't much to do
>> with the templating ... but on one side it affects the display / use
>> of some data.
>>
>> It would be great if we could add more flexibility of the object
>> model ... for example here at maxspot we don't need the value "info
>> on mass transportation" ... but for sure it would be great, if we /
>> other groups could add some other categories without customizing the
>> code of WiFiDog itself.
>>
>> So far, Max
>>
>> Am 26.03.2006 um 01:13 schrieb Benoit Grégoire:
>>
>>> Hello fellow developers and users,
>>>
>>> I took the time to try and write down the consensus on wifidog
>>> customization
>>> befor I start on HTML and CSS cleanups (as I understand it).  For
>>> now, this
>>> is design documentation as not everything is implemented.  I would
>>> very much
>>> appreciate your feedback on the main document
>>> (http://dev.wifidog.org/wiki/doc/developer/PortalCustomization) but
>>> more
>>> importantly on the proposed CSS structural layout diagram:
>>> https://dev.wifidog.org/attachment/wiki/doc/developer/
>>> PortalCustomization/structural_layout_wifidog.pdf
>>>
>>> Specifically, do you think we need anything more id, class or makup-
>>> wise to
>>> allow for any customization you may want to do?
>>>
>>> Also, if you have any question or would like clarification for one
>>> of these
>>> documents, don't hesitate to ask here or on IRC.
>>>
>>> Good night,
>>> --
>>> Benoit Grégoire, http://benoitg.coeus.ca/
>>> _______________________________________________
>>> WiFiDog mailing list
>>> WiFiDog at listes.ilesansfil.org
>>> http://listes.ilesansfil.org/cgi-bin/mailman/listinfo/wifidog
>>
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.1 (Darwin)
>>
>> iD8DBQFEJ134+BKgC+eQ3ooRArh0AJ9euXIroJdPGwRyqzU6iIArxwvAkQCgg/v4
>> u5zRXAFKP1JYH1728/akPpM=
>> =dTZK
>> -----END PGP SIGNATURE-----
>> _______________________________________________
>> WiFiDog mailing list
>> WiFiDog at listes.ilesansfil.org
>> http://listes.ilesansfil.org/cgi-bin/mailman/listinfo/wifidog
>>
>
>
> --
> Ben Crulli
> _______________________________________________
> WiFiDog mailing list
> WiFiDog at listes.ilesansfil.org
> http://listes.ilesansfil.org/cgi-bin/mailman/listinfo/wifidog
>

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)

iD8DBQFEJ2M8+BKgC+eQ3ooRAiI9AJ0eTKAZ1M+MG4c8xBMoC7HQ7+q7fACgnpsZ
j+KW/QuXFAOUzJON6UiQkz8=
=dw73
-----END PGP SIGNATURE-----