Re: [Haifux] W2L0, second thoughts about kdevelop
I have tried Kdevelop myself, I don't remember what version it was but I do not recall any need to running autoconf script or knowing about autoconf at all. I do remember that it gnerated a configure script automaticly. Of course it is beyod the scope of the lecture to talk about QT application generations but to show a simple application, I think it can be done. I myself wrote a simple window with a menu in less then 30 minutes and that was when I had no idea of how QT works so it took me about 30 minutes including reading the documentation. -- Ori Idan On Sunday 14 September 2003 03:53 pm, Maor Meir wrote: I initially thought showing kdevelop in W2L0 whould be a good idea due to its similarity to M$ Visual C++. I installed kdevelop 2.1.3 (not the latest) and tried to write a hello world program, I quickly found myself running autoconf configure scripts. When looking at the built-in documentation I found plenty if information on using kdevelop to create QT applications, this is way beyond the scope of W2L lecture 0. kdevelop can be used for simpler projects, this is not what it is designed for. I can not in good faith recommend this tool for newbies. unless someone has another opinion(speak up) I will leave kdevelop out of W2L0. Meir. P.s I also said I will add Makefile basics, a first draft of the content (no formatting) will be available for review later today. -- Haifa Linux Club Mailing List (http://www.haifux.org) To unsub send an empty message to [EMAIL PROTECTED] -- Haifa Linux Club Mailing List (http://www.haifux.org) To unsub send an empty message to [EMAIL PROTECTED]
[Haifux] Palladium's Immunity against Hardware Attacks
Check here for a Cryptogram article about Palladium: http://www.counterpane.com/crypto-gram-0208.html#1 It says: Microsoft readily acknowledges that Pd will not be secure against hardware attacks. They spend some effort making the secure processor annoying to pry secrets out of, but not a whole lot of effort. They assume that the tamper-resistance will be defeated. It is their intention to design the system so that hardware attacks do not result in class breaks: that breaking one machine doesn't help you break any others. A few people thought the opposite was the fact in one of our previous meetings. Regards, Shlomi Fish -- Shlomi Fish[EMAIL PROTECTED] Home Page: http://t2.technion.ac.il/~shlomif/ An apple a day will keep a doctor away. Two apples a day will keep two doctors away. Falk Fish -- Haifa Linux Club Mailing List (http://www.haifux.org) To unsub send an empty message to [EMAIL PROTECTED]
Re: [Haifux] W2L0, second thoughts about kdevelop
On Sunday 14 September 2003 15:53, Maor Meir wrote: When looking at the built-in documentation I found plenty if information on using kdevelop to create QT applications, this is way beyond the scope of W2L lecture 0. Actually, creating any decent GUI program is way beyond the scope for newbies (whatever platform/environment they use): - Heavy OOP - Callbacks/Listeners/Slots/What-you-call-them-today - Containers and layout management - Event propagation and widget (instances) tree Not exactly Introduction for Programming stuff. However, Kdevelop may be used as a show off stuff if it would be shown together with other tools. Examples: - Anjuta - Eclipse (the free software one...) - If there's an Emacs guru I would ask him to demo it as well (but drop it if there isn't someone who can really make it shine). Showing several tools of the same family (IDE's) is important because a lot of our potential audience suffers from uni-dimentional vision simptom caused by inhaling too much Visual-Studio for too long time. It is extremely important to show there are *different* strategies to reach the same goal. Once they understand this -- they already got half of what Linux is all about. -- Oron Peled Voice/Fax: +972-4-8228492 [EMAIL PROTECTED] http://www.actcom.co.il/~oron Windows is NOT a virus: a virus is small and efficient. --Jonathan Leffler, Informix -- Haifa Linux Club Mailing List (http://www.haifux.org) To unsub send an empty message to [EMAIL PROTECTED]
Re: [Haifux] W2L0, second thoughts about kdevelop
On Sun, 14 Sep 2003, Oron Peled wrote: However, Kdevelop may be used as a show off stuff if it would be shown together with other tools. Examples: - Anjuta - Eclipse (the free software one...) - If there's an Emacs guru I would ask him to demo it as well (but drop it if there isn't someone who can really make it shine). Showing several tools of the same family (IDE's) is important because a lot of our potential audience suffers from uni-dimentional vision simptom caused by inhaling too much Visual-Studio for too long time. W2L0 contains several slides aimed at teaching basic use of emacs as opposed to showing off. The introduction lecture (#1) may have demonstrations for showing off aspects of linux. But I am not sure how much showing off sould be put in the introduction to programing under GNU/Linux. I could easily throw in a demonstration of half a dozen advanced Emacs edditing tricks. The real power of emacs can only be seen by giving a (very)complex editing task and solving it quickly by use of tools such as recovering old clipps from kill ring, keyboard macros, abbrev mode auto-completion, etc. To truely show the full power of emacs the task needs to be very complicated, if I explain what I am doing, it won't seem like black magic but it may cause information overload and make them not remember emacs basics and/or give the impretion emacs is too complicated. It I don't explain what I am doing, it will look like dark magic and it would just be showing off with out teaching anything. I wan't planning on mentioning Java at all, I think I am still not planning to mention Java. I have very little Anjuta experience(and some more with Glade). I don't think I should go in to Anjuta for the same reasons I rejected kdevelop. It is extremely important to show there are *different* strategies to reach the same goal. Once they understand this -- they already got half of what Linux is all about. This might be acomplished simply by teaching one way, and at the end mention a short list of what we didn't show you, just a list with screen shots and two sentences on half a dozen usefull IDEs. with out demonstrations or teaching anything about usage. Meir. -- Haifa Linux Club Mailing List (http://www.haifux.org) To unsub send an empty message to [EMAIL PROTECTED]
[Haifux] W2L0 Makefile basics, draft
As promissed: attached is the text I wrote for basic Makefile use to add to W2L0 look it over, comment, I'll fix as necessary and than shlomi could HTMLize it to fit with the rest of the beautyfied lecture slides. Meir. Makefiles are a way to define how your project is to be built. The make tool reads this file and compiles your project properly and efficiently, recompling files that were changed and files which dpend on them. Using the correct compile command at each stage. For large projects this is a must, and in many cases it is convinient also for small projects with only half a dozen source files. Makefile basics: A makefile is built out of a set of targets, each of which dpends on certain files (which may also be targets) and has a compile command to build the target as in: foo: foo.o helper.o gcc -Wall foo.o helper.o -o foo bar: bar.o helper.o gcc -Wall bar.o helper.o -o bar bar.o: bar.c gcc bar.c -c -o bar foo.o: foo.c foo.h gcc -ansi -Wall -c foo.c -o foo.o To run make one types: make [target_name] if no target is specified the first target in the makefile is used. Makefile variables: we can define variables in makefiles to make the writing shorter and the modifications easier. rewriting previos makefile with variables and extra targets: CC= gcc LD= gcc CC_FLAGS = -ansi -Wall -c LD_FLAGS = -Wall all: foo bar foo: foo.o helper.o $(LD) $(LD_FLAGS) foo.o helper.o -o foo bar: bar.o helper.o $(LD) $(LD_FLAGS) bar.o helper.o -o bar bar: bar.c $(CC) $(CC_FLAGS) bar.c foo.o: foo.c foo.h $(CC) $(CC_FLAGS) foo.c clean: rm -f *.o foo bar behind Makefile magic: Makefiles watch the time-stamps for files, if the source files time stamps are newer than the target, the target needs to be rebuilt and any targets depending on it need to be rebuilt as well. Finding dependencies: This can be done automaticly to a great deal using gcc -M source.c
Re: [Haifux] W2L0 Makefile basics, draft
On Mon, 15 Sep 2003, Maor Meir wrote: As promissed: attached is the text I wrote for basic Makefile use to add to W2L0 look it over, comment, I'll fix as necessary and than shlomi could HTMLize it to fit with the rest of the beautyfied lecture slides. you basically don't give examples of how the makefile's run looks. i assume you do intend to demo it during the lecture? the explanations are too terse the way they are - remember that your audiance does not have the notion of Makefile - it is this notion that should be explained, not just the technicalities and syntax. i'll try writing a more detailed example tonight. by the way, you could try looking at the lupg 'writing makefiles' tutorial for ideas (or you could not, ofcourse ;) ). -- guy For world domination - press 1, or dial 0, and please hold, for the creator. -- nob o. dy -- Haifa Linux Club Mailing List (http://www.haifux.org) To unsub send an empty message to [EMAIL PROTECTED]
