Search options (Page 2 of 13)

because he's likely not using asp.net's bloated infrastructure to do this (at least I'd hope not).

a .net version of punbb seems perverse to me though.

google "byte order marks"

its the utf8 encoding header of the file.  I don't think the server should be encoding its output like that.

looks nice m8.  its cool to see people really integrating it instead of just throwing it on the site.  I've been too lazy to get mine that integrated but the results are nice.

nice!

create a new group.  create a new forum, edit the permissions for that forum so only the members of the new group you just made can read / post to the forums.  change the groups of the ppl you want to see that forum.

I'd still like to know how you're doing your seo urls.

most .net forums you're going to have to pay for.  any free ones are going to be written by some kid while he's reading one of those C# in 30 days books, and its going to suck.

community server has forums, but you have to buy the software and at 300 bucks and they require you to keep their "Community Server" logo, and run their ads, thats a bit excessive ($450 w/ out those things is still a pretty sour price tag).

looks great!  would you be opposed to sharing your url mod?

oop is a concept (which btw is not strictly enforced by C++ because of its interoperability with C) enforced by a complier or interpreter. 

to that end, the concepts produced by such a thought, when implemented in a language, provide more reliability of data integrity than languages that allow global access of data.

lets say for a second that punbb was an oo implementation.  data access, configuration, and functionality were totally internal / private.  lets say that it had an extension framework that consisted of a base "extension" object from which one could inherit and do whatever with.  by using this type of model, one could never access the actual pun_config or db objects and the maintainer of this board could ensure that no extension / plugin could ever take a board down because mods never have access to internal core code, variables, or functionality. 

in my opinion, procedural programming concepts just don't provide the necessary functionality to produce reusable, extensible and data protected applications.  scripting is another thing, that I'm leaving out of this, but just on a conceptual level, I sticking by what I've said.

its a random bug.  chances are, those double posts are no longer there.  it shows up every now and then, then disappears.

but thats something completely different. 

only reason I say this is because most of my career I've been a platform developer.  producing an sdk which allows some random developer to bring your system crashing down is never a good thing.  A strict API for accessing the system is far safer than providing some global access to data that the "black box" uses. Its not always avoidable (esp when we're talking about kernel level driver interaction), but there is a reason why operating systems are written using OOP. 

In general (especially with crappy implementations which abound) I think web development is best suited in a quasi-oop manner, and there is a happy medium between component, and OOP in web development especially when you have a versatile language like PHP to work with.  outside of the web however, I think its far more reliable in a strict OO manner.

inheritance enforces a common functionality.  encapsulation ensures that I never step on common variables that lead to hard to find, and hard to fix once found problems.  strict object oriented programming removes global functions and variables that typically forces the developer to place that functionality in some common object.

being able to segment code into namespaces / packages / libraries further encapsulates objects and their members.  inheriting leaves less room for error as children typically inherit parent classes functionality, which means you write an object (like a base business object) that contains core level functionality (like database persistence) and all 900 of your implementing objects contain the same functionality.  if you correct a bug in the base class, all 900 benefit from it. 

lastly, it saves time by being able to reuse specific application logic while hiding or overriding other functionality.

I hated OOP when I first started learning it, but now could not do without it.