|
yep, it's probaly only the one aspect that I consider most interesting in the Judas figure..
Smith rocks. He's my hero since the very moment he "took away" Neo's mouth im Mx 1..
"Der Geist des Kriegers ist erwacht / Ich hab die Macht" StS
sighist | Agile Programming | doxygen
|
|
|
|
|
peterchen wrote:
Smith rocks.
At last, i meet somebody like me. Everybody thought I was crazy 'cos I like Smith. Now I know I'm not alone.
Hugo Weaving really does a good job.
Vikram.
-----------------------------
My site due for a massive update.
Never see a BSOD again - FREE!
"Do not give redundant error messages again and again." - A classmate of mine, while giving a class talk on error detection in compiler design.
|
|
|
|
|
Vikram Punathambekar wrote:
peterchen wrote:
Smith rocks.
I agree - Smith certainly rocks, in that he's the most funny and entertaining character IMHO.
Paul
|
|
|
|
|
4)Merowinger sounds a bit like Merovingian to me, they we're some french kings
Merovingian_Dynasty[^]
Personally I reckon that they're gonna find themselves in a matrix within a matrix ( he he ) in the third one, cool !
|
|
|
|
|
Ahh thanks! I knew of the Merovingians as a dynasty (Merowinger is the german name), but I didn't expect them to have hung around in France (More easternish)
[edit] It's Franken, not France. So actually he SHOULD have been a good old german villain!!! [/edit]
"Der Geist des Kriegers ist erwacht / Ich hab die Macht" StS
sighist | Agile Programming | doxygen
|
|
|
|
|
peterchen wrote:
It's Franken, not France. So actually he SHOULD have been a good old german villain!!!
I guess german villians are too cheesy these days. Also the key feature of that guy was his arrogance ( sniffing the wine and all that ) and what better character to choose to portray this than a french dude
( Btw I love the french personally, its just their percieved as arrogant )
|
|
|
|
|
peterchen wrote:
Is Neo inside the Matrix / Another matrix / outside when he stop the sentinels?
That's kindof what I was thinking. I'd almost put money on that we'll see this in the next movie.
Brad Jennings
"You're mom is nice. Mind if I go out with her?" - Jörgen Sigvardsson
|
|
|
|
|
peterchen wrote:
Animatrix says "the machines founded 01 in the cradle of humanity". Zero-One == ZION?
No, IMO
01 was above ground for one, twas a sprawling city. I suspect it was also bombed pretty badly. While the nukes did not hurt the machines it probably did hurt the city.
peterchen wrote:
why did he have a French accent?
Umm, because he was French? Must every actor in the Matrix be a yank? And if the Wachowski brothers threw in a French bady just to ridicule the French then my respect of them, the brothers, goes way down.
peterchen wrote:
So yes, maybe the "traitor of Zion" is Smith. He's already there... The real one? The Matrixed one?
Yeah! I loved that bit, so cool. I don't think Zion is inside another Matrix, it is just too much of an obvious twist in the tale.
Anyway, we will see with Revolutions. I am waiting till then
p.s. Might get some time this evening to send you my thoughts on the snippet library.
Paul Watson Bluegrass Cape Town, South Africa
Chris Losinger wrote:
i hate needles so much i can't even imagine allowing one near The Little Programmer
|
|
|
|
|
Paul Watson wrote:
01 was above ground for one
Dammit! There goes a nice theory!
Paul Watson wrote:
Umm, because he was French?
Merovingans are Franken (Germans), not French.... Anyway, it was just my first reaction: that's what the world was waiting for: a "loath-me-baddie" with french accent
Zion in/out: I really like neither of the two interpretations: Zion being a matrix, nor Neo getting ueberpowers in RL. That's why the idea of two zions - a real, and a matrixed one - are so nice - I could put everything I liked into the zion I want...
"Der Geist des Kriegers ist erwacht / Ich hab die Macht" StS
sighist | Agile Programming | doxygen
|
|
|
|
|
peterchen wrote:
Dammit! There goes a nice theory!
hehe, it is a nice one.
Zion apparently is very, very deep. They speak of near the Earths core which shields them from the Machines. Of course I doubt it is actually near the core. But still very deep.
As we saw it is this big cylindrical kind of city, maybe it is the basement of 01? A long forgotten storage area of 01?
I like the symbolism and link that would come from Zion and 01 being so closely related. Using the remnants of 01 to build Zion.
peterchen wrote:
I could put everything I liked into the zion I want...
Yeah, including a nekkid Monica Belluci (Merovingan's wife, you know, the one who wore surgical latex as a dress.)
Paul Watson Bluegrass Cape Town, South Africa
Chris Losinger wrote:
i hate needles so much i can't even imagine allowing one near The Little Programmer
|
|
|
|
|
Paul Watson wrote:
maybe it is the basement of 01? A long forgotten storage area of 01?
Thank you
Paul Watson wrote:
Monica Belluci
It's less where you put Monica Into, but what you put.... :umm: :err:
Anyway, I'd prefer a night out with Tri or a moonlight hike with Phoebe over any putting around with Monica.
"Der Geist des Kriegers ist erwacht / Ich hab die Macht" StS
sighist | Agile Programming | doxygen
|
|
|
|
|
peterchen wrote:
Anyway, I'd prefer a night out with Tri or a moonlight hike with Phoebe over any putting around with Monica
True. Monica Belluci is a Dream Woman. Trinity or Phoebe are Real Women. I can easily imagine Monica and I can easily dream about her. But I could never see her in RL, it would be odd. Trinity and Phoebe though I can imagine having dinner with, sitting in a park with, having a fight with etc.
Not that Jada Pinkit Smith is my kind at all. Trinity is of course quite lovely.
peterchen wrote:
It's less where you put Monica Into, but what you put.... :umm: :err:
Any CPian female reading this must be rolling their eyes and marking us down as typical males.
Paul Watson Bluegrass Cape Town, South Africa
Chris Losinger wrote:
i hate needles so much i can't even imagine allowing one near The Little Programmer
|
|
|
|
|
|
|
true to my socialist upbringing - "You made the suggestion, you realize it" - let's get things rolling. I picked the code snippet library both out of curiosity, and as a project with early results yet potential to grow.
Abstract:Application to manage a collection of code snippets, working standalone, from a centralized server, or peer-to-peer.
Note: These are my ideas, and assumptions. Correct me if I'm wrong, and feel free to discuss.
First Step - Standalone Client
The Standalone Client enables a single coder to store and reuse small functions, classes, and "unstructured" code sequences of his favorite languages. A desktop application that interfaces the development environment via the clipboard, stores data language-neutral, with extensible meta data, and allows basic organization.
A good paradigm for storing a snippet seem to be files, and using folder as structural criteria. This allows users to "reuse" their organization behavior for loosely coupled data.
Storing each snippet in a physical file has the advantage that cleanup, moving around, renaming, and basic searching comes "for free", again according to the user's choice.
Scalability, might require other storage mechanisms as well.
Benefits: Early "ROI" - we have something "to deliver". Plus, coders can already build their snippet libraries for later sharing.
Networking - Central Server
This will enable closed workgroups to build a common database, and to exchange snippets. A simple Intranet-version could be dereived from the stand-alone version by connecting to a shared folder, or allowing the inclusion fo a shared folder. A web application would allow sharing the data over the internet. Ideally, the standalone application can connect to any folder, shared folder, or URL to access (or at least retrieve) a snippet library.
The Web Application would allwo widest availability, while the standalone application would be targeted to a common interface with location transparency*.
Networking - Peer to Peer
For loosely coupled, server-free application, the client could "piggy-back" Instant Messengers and other P2P software. The technical possibilities to interface common clients need to be evaluated.
general P2P benefits - zero administration setups, running cost is shared between the participants, loosely organized. Plus, it opens up "connections" between the server-based libraries.
Scalability
To make the snippet library feasible for a site of the size of CP (the "ultimate goal", in the following called "big server"), various issues must be solved:
a) defining interfaces and "reuse" between stabdalone and "big server" application. "Read-only" access to the big server is a "certainly possible minimum"
b) Advanced Description: "A snippet belongs to one cat" isn't enough for a library of this size. While a non-repeating strict hierarchy is still desirable, advanced grouping mechanisms (like m:n snippet-category mapping, or keywords) is required.
c) Data Storage: with respect to storage size, maintenance and accessibility, snippet files might be bad.
d) Indexing: advanced search is necessary, without bloating the necessary meta information. Storign the index in a database is of essence for acceptable performance.
e) Quality: Such a large databasse surely clutters up with... less recommended code. Voting (like on CP, perferring main contributors) would be nice, but requires
f) User Management - this should ultimately be able to integrate with "external" user managements, like the one on CP.
g) ???
other topics
a) Integration with Development environments
b) Language-specific Code Representation ("beautifier")
c) Keyword replacement (e.g. snippet "reverse a 'TYPE *' vector in place" would allow me to specify type, and vector name)
d) Extract/Embed meta information from/in language-specific comments
e) selectable "comment header templates" for functions and classes
f) ???
Whew. That's it. For now.
*) shouldn't that be "location opacity"?
"Der Geist des Kriegers ist erwacht / Ich hab die Macht" StS
sighist | Agile Programming | doxygen
|
|
|
|
|
Did you get my email today about the code snippet library and my secret plan?
Jason Henderson My articles
"The best argument against democracy is a five-minute conversation with the average voter." - Winston Churchill
|
|
|
|
|
Yes - Paul is basically interested, and roughly agrees with the proposal. We just wanted to "sync" some basic ideas in the next days before we contact you again. Fnord.
"Der Geist des Kriegers ist erwacht / Ich hab die Macht" StS
sighist | Agile Programming | doxygen
|
|
|
|
|
You will be my "Second Foundation." If you've ever read Isaac Asimov's Foundation trilogy, then you may understand what I mean.
Jason Henderson My articles
"The best argument against democracy is a five-minute conversation with the average voter." - Winston Churchill
|
|
|
|
|
You are going to lock yourself up in a secret vault and at key moments in psychohistory reveal yourself with wise words in holographic form?
Wow. I thought we were just making a snippet library
p.s. Giving all my thoughts to Peterchen now.
Paul Watson Bluegrass Cape Town, South Africa
Chris Losinger wrote:
i hate needles so much i can't even imagine allowing one near The Little Programmer
|
|
|
|
|
Paul Watson wrote:
You are going to lock yourself up in a secret vault and at key moments in psychohistory reveal yourself with wise words in holographic form?
Actually, I'll be dead, but the rest of it is right on. Just call me Hari Seldon.
I'm glad someone else has read these books, but where is this Second Foundation I speak of? right under your nose
I love Asimov so much I'll name a child after him. Asimov Henderson.
Paul Watson wrote:
p.s. Giving all my thoughts to Peterchen now.
good man
Jason Henderson My articles
"The best argument against democracy is a five-minute conversation with the average voter." - Winston Churchill
|
|
|
|
|
Suggestions about the Code Snippet library :
- the infrastructure is already here, it's VS.NET.
- there's an attempt for a code snippet library as a standalone app. Look here[^], API-guide (2.2MB) has a .NET tab with in-context samples. Categorization using the tree is fine and fast to browse. Me like it. :-!
- peer-to-peer ? May be you are going a bit too far here. Centralized with an update every month or so is already more than enough. Anyone interested in seamless updates could use the MS BITS download library (used in Windows update).
Last but not least, an issue : you are not likely to make business with this. That's unfortunately IMHO the kind of stuff which are hard to sell by themselves.
|
|
|
|
|
Stephane:
Thanks for your feedback.
I wrote this mainly as input for CodeProject Projects. basically, Jason, Paul and I are still fiddling around how to continue with it. Until then I appeciate discussions, but want to keep the ball low.
So there's no "make money" idea in it. Trust me, the things I consider marketable I wouldn't analyze that publicly.
Technically, it's just a blog of ideas. Paul agrees with the basic challenge: creating a infrastructure that handles both one-dev standalone and 100k users in a server environment. P2P is just another means of sharing. It might be valuable as server-free exchange for standalone users, and as a "tunnel" between server-based nets.
I'll look into API guide - although it seems to be made for something else.
"Der Geist des Kriegers ist erwacht / Ich hab die Macht" StS
sighist | Agile Programming | doxygen
|
|
|
|
|
Ok IMO there are two tracks to this project.
One is to rehash all the existing snippet library ideas and produce a good but rather unoriginal system. I will get bored on that track and be lazy, the result will be nice and useful but... well we are doing this in our spare time and I want a bit more than just "nice" and "useful" for my spare time
Two is more ambitious, harder to do but ultimately more fulfilling. Two however will cover the above quite easily.
Let me explain.
I see three usage scenarios which are key in understanding what it is we are to produce.
- Personal/Standalone coder. This is Christian Graus. He does not want P2P, he does not want other peoples code, he does not want sharing and rating and community features. He does not want to know about the XML backbone or setting up a code-server or fannying about with webservices. He does not want to even have to login to the application to use it. He wants to be able to store his often used pieces of code and to be able to drag them into his applications with the least amount of fuss possible. For him a standalone client or a VS/.NET Add-In are perfect. No admin consoles for the code-server, no registration and such. Just right-click-store-code, right-click-insert code. The system should let him store just a piece of code without even a title required as well as let him title, categorise and keyword code to make searching easy.
- CodeTeam This is a bunch of guys in a company who want to share code amongst each other over a LAN. The company may say "Here is the preferred code for sorting an array in JavaScript" and it will be available to all. The "code-tree" will be editable by all on the network, code can be added and removed, used and abused etc. This sytem will have simple community features. No ratings, blocking and such. Also each client can have their own personal code-tree independant of the Company code-tree. Also a company may want to setup a template for the data-structure of code snippets to ensure items on the Company code-tree are of a certain quality (title, description, author, usage etc.) This scenario though does not include the web-facing component as it is meant to be kept all in house.
- CodeCommunity This is CP on steriods This is the more ambitious idea of mine. Basically someone will setup a community server and then multiple clients can connect to the server and start sharing code. Each client can of course have their own personal code-tree on their machine. The Community code-tree though will be moderated. Someone submits a new item then it goes into the Un-edited reader contributions section An editor using the client app would then review the snippet and either leave it un-edited (and not officially part of the CCT) or move it into an official Category/Folder. The author of the snippet can edit their item, but then it is reviewed before the edit goes "live". etc. etc. So CodeCommunity is like a internet application version of CP. A bit like Artifact in that way, but without the waffley bits, confusing setup and odd way of doing things. Also a client can connect to multiple CodeCommunity servers as well as to a Company code-tree and have their own personal code-tree. I was thinking a namespace/domain type system would work for that.
Ok so those three scenarios tell me that we need a Client app (standalone and VS.NET Add-In), a Storage service and a Community interface. The Community bit can be built later as really what it is in my mind is simply a web-interface (web-services I assume) to the Storage service. The Storage service will be the key naturally.
Don't shudder when I say I think XML will be a good mechanism for storing the snippets. It is overhyped but it is pretty damned useful and it will make sending snippets over the wires easier, especially through web-services.
Not only that but, and here is another grand idea, XML is, no sh*t, extensible. Code snippets rarely follow a rigid format. Some will have all the fields under the sun filled out, others will just be a code block and thats it. I get frustrated with snippet libraries that ask me for "target platform" when it comes to a piece of HTML, what the heck am I supposed to fill in there? It should not even ask me that. So we can have XML templates. One for C++/C#/VB/Fortran code, another for CSS, another for HTML etc. When someone creates a new snippet it either asks them which template or preferably it knows which template to use based on the category/folder they are creating in or from inspecting the code in the clipboard.
The display would then inspect the snippet, see that it is a HTML templated snippet and display accordingly. We can even offer interfaces which allow people to perform certain actions on specific snippet types. e.g. If HTML then run macro XYZ when item is selected.
I am very much up for a flexible system. One that does not make C++ coders happy but makes HTML coders curse the day it was born.
Also another key of using XML is with the CodeCommunity aspect; It makes it dead easy for CodeProject to merge in snippets from CodeGuru (hypothetically speaking of course, we don't need their steeennkiiing code) or for the snippets to be re-published to an entirely different system. Maybe someone wants to create a client which runs on WinCE, they are free and able to easily do so because the code-tree is exposed by a common web-service interface which streams out XML which they can then XSL or de-serialise or whatever they want to their WinCE client.
It would blow my mind if Chris made all the articles on Code Project available like that. That would be a huge step up IMO. (Of course ad-revenue generation will have to be carefully though through. But when you syndicate your content you can charge for it without ads. Who knows, but I like the idea and the devilish details can sod off till later.)
Ok so that is my idea. The Client, the Storage and the Community interface. A person can choose just to install the Client and a personal Storage and never share with anyone. Or they can download the Storage service, put it on a company server and then have co-workers in the company download the Clients and share in-house. Or Bob can download the Storage and Community interface, setup a server and have a bunch of users with Clients connect and share.
Notes/Ideas:
- Snippet items must definitley be stored as seperate physical files. This may be bad for performance but it will ensure Christian Graus can say "Sod it, I hate this app" then go into the store folder, copy all his code out as files and then kill the app. No proprietary single-file storage mechanism, no "exporting" to get at your code etc. Search performance can easily be managed by managing a search index file where with each edit, delete or update the index is updated. It also makes it easy to email files to co-workers or friends who do not have the app. The system must not lock people into using it for their code, it needs to be open like that.
- Storage of binary files (maybe a screenshot of the code in action or a compiled assembly DLL)
- Syntax colouring
- Do we need versioning? I like the idea but it might prove to be more complex than benefitial
- Multi-categorisation: Most definitley snippets should be able to live in different categories/folders and right from the start. Retro-fitting a one-to-many system to a many-to-many system is never fun
- Online/offline handling must be seamless. No crashing if a community server goes down, cached items still available etc.
- Bookmarking of items and "Download to Personal Code-Tree" functionality
- For the CodeCommunity and CodeTeam systems a robust security model is needed so that we can assign Editors, Administrators etc.
- Put watchers on items and be notified when they change
- I am not too keen on the P2P idea because it will result in a free-for-all fight in the code-tree structure. I don't mind using P2P for discovery and load distribution. Clients can directly connect to each other if needed. It might be overkill having P2P though.
- Super Simple Installation Mode: This is for Christian Graus. When he double clicks that Setup.exe it must only ask him where to put the files and thats it. No "Please rovide a CodeCommunity username and password" or "Would you like to share?" etc. I can see CG cancelling a setup if it bothers him with irrelevant questions. Hard core okes must not be bothered. I want their respect for this system, if we can do that then we have done an amazing thing
I must put together a Visio file of how I see the architecture working. Client, Storage and Community/Web-interface.
So there you go. I have plenty more thoughts on the matter but that is the basic idea I have.
Paul Watson Bluegrass Cape Town, South Africa
Chris Losinger wrote:
i hate needles so much i can't even imagine allowing one near The Little Programmer
|
|
|
|
|
Fantastic ideas Paul.
CodeCommunity sounds like a big undertaking, but the other two are very doable in the short term. Don't get me wrong, CodeCo is a great idea but I think it could wait. Design around the idea though, so it will be easy to implement. But, if you and peterchen think it can be done now, then all the better, and "Go for it!"
Paul Watson wrote:
Don't shudder when I say I think XML will be a good mechanism for storing the snippets. It is overhyped but it is pretty damned useful and it will make sending snippets over the wires easier, especially through web-services.
We all know that XML is just text, but its a standard and there are a lot of powerful things that can and are being done with it. I have no problem with it being used.
Jason Henderson latest CPP news
"If you are going through hell, keep going." - Winston Churchill
|
|
|
|
|
CodeCommunity sounds like a big undertaking, but the other two are very doable in the short term.
Exactly right. The main thing is the central Storage, then next is the Client. That caters for everything but the more ambitious and open CodeCo idea.
I see CodeCo as being an add-on to the Storage layer. All it really is is a layer of web-services to interface with the Storage and a few extra bells and whistles to manage the herd of buttered kittens that a community of coders can be.
So certainly the Storage and Client are doable and will have good results relatively quickly. then when we have the Storage rock solid the CodeCo can be started.
Paul Watson Bluegrass Cape Town, South Africa
Chris Losinger wrote:
i hate needles so much i can't even imagine allowing one near The Little Programmer
|
|
|
|
|