• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
licencing code : was: CSS Integration and SubComponents (Partial components?)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

licencing code : was: CSS Integration and SubComponents (Partial components?)


  • Subject: licencing code : was: CSS Integration and SubComponents (Partial components?)
  • From: Jean-François Veillette <email@hidden>
  • Date: Wed, 27 Oct 2004 13:03:59 -0400


note 2: I would like to share that code, but I would need first the autorisation of my employer. I'm in vacation right now, if you want that code, let me know, I'll try to post it to wocode/wodev when I'm back to work.

Good news !
I got the autorisation to make the code public.
But I have first to make sure the code is clear to go public (copyright notices, etc.). So for those of you who would like to see that code, be patient :-)

It's going to be the first time I open source code to make it public, I'm completely new to this legal stuff. I know that there is many type of licences available, should I care ? why ? what can happen if there is no licence ?

What are your experiences with opening your source code, licence, etc ?
What are the details ? just comments at the start of every files ? separate file detailing the licence ?

thanks,

- jfv


Over time, we have build a very nice architecture for such things ...

- we use a common superclass for all of our wo-components.
- in there, we have the following method :
public void addJSRessourceNamed(WOResponse res, String name)
public void addCSSRessourceNamed(WOResponse res, String name)


and what they do is add the corresponding
<script language="JavaScript" src=" urlToResourceNamed "></script>
or
<link rel="stylesheet" href=" urlToResourceNamed "/>


to the response's [head] section.

So a generic component for a calendar for example, could add multiple .css and/or .js to the response stream.
We have wrapped jscalendar (http://dynarch.com/mishoo/calendar.epl), using this technique. Now the integration of this component, is just a matter of drag-drop into the page. we originally had to manually do the .js and .css import for each of the sub(-sub)-components at the page level, this was a (little) pain to maintain.
Now a component comes with all it needs for .js and .css. it's like a component 'bundle'.

I would suggest you to evaluate this implentation path, it's worth it !

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >CSS Integration and SubComponents (Partial components?) (From: Jeremy Matthews <email@hidden>)
 >Re: CSS Integration and SubComponents (Partial components?) (From: Jean-François Veillette <email@hidden>)

  • Prev by Date: Re: WO & Lucene
  • Next by Date: Re: NSDictionary and WOPopup Question
  • Previous by thread: Re: CSS Integration and SubComponents (Partial components?)
  • Next by thread: JavaMail/JMTA help request
  • Index(es):
    • Date
    • Thread