Evaluating a simplified component mechanism, feedback required

5 views
Skip to first unread message

rossputin

unread,
Mar 14, 2013, 11:13:04 AM3/14/13
to silk...@googlegroups.com
Hi Guys.

We are considering a simplified component mechanism in a little rewrite that has been ongoing for a couple of weeks.

Previously with Silk you could use the following types of component:

- local (in 'component' directory)
- user installed in .silk repository (shared across projects locally)
- silk core (part of the distribution) (shared by all silk users)

There are elements we like about this and others we do not like.

We like the ability to create quick throw away components locally, relevant only to the specific project you are working on.
We dislike the complexity of getting components added to the core distribution (no mechanism was ever thought up for this).
We dislike the large amount of code required to manage components etc in the Silk codebase.

Part of our rewrite has been to switch to Twitter Bower to manage dependencies and components (it did not exist when we wrote the original Scala Silk).  This strips out a load of maintenance.  We think that components can be further simplified though.

At this point our little rewrite is more or less functional, minus error handling, and it only looks for components in one place (a local repo managed by bower).

We are evaluating putting local components back in and wanted your feedback.

Cheers.

Barrie McGuire

unread,
Mar 14, 2013, 1:25:05 PM3/14/13
to silk...@googlegroups.com
Howdy,

I think local components do have value, however with proper namespacing there's no need to have several mechanisms.  We could just re-use bower?

ta,
Barrie

Kind Regards,
Barrie McGuire

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

BHEAP LIMITED
Unit 33
1 Winnall Valley Road
Winchester
Hampshire
SO23 0LD

Registration Number: 07510939
Registered in England and Wales

--
You received this message because you are subscribed to the Google Groups "Silk Web Toolkit User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to silk-user+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

rossputin

unread,
Mar 14, 2013, 2:22:43 PM3/14/13
to silk...@googlegroups.com
My thoughts too, ta.

rossputin

unread,
Mar 15, 2013, 10:12:28 AM3/15/13
to silk...@googlegroups.com
You know what though, as they are local, there would be no need for any kind of package management... they are just in the specific project in terms of VCS etc.

They do feel quite natural in this regard.


On Thursday, March 14, 2013 5:25:05 PM UTC, Barrie McGuire wrote:
Reply all
Reply to author
Forward
0 new messages